Rename vues to multiword #118
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WIP: work on course_settings WIP: continued work on the course settings WIP: continued work on course_settings. TEST: mojolicious route testing for settings. WIP: continued work on course settings
WIP: allow default settings to be defined in an override file.
WIP: fix up tests and general cleanup. WIP: fix up tests and general cleanup. FIX: errors after rebase
WIP: switch pages/components to multi-word
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In a more recent version of vue-eslint, there is a requirement that vue pages and components to be multiword. This is designed not conflict with future html tags. See https://eslint.vuejs.org/rules/multi-word-component-names.html
This changes no functionality, just renaming files and updating affected components.
This relies on #106, which has some UI changes. We should push this through quickly so any updates on components won't conflict in two files.